Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 36aa7f6e1e2fcf4bde01eb58bf7c176ab3964a7150d58b835a9168df68ceb768

Tx prefix hash: 78ef7b2d9eee8a04cfe23e429b5aaa68c3989a51797e02d8bb325b13f7a41e85
Tx public key: 06740e9f3fd9fb5cf2b567712f9538663599e44f48c211a006222d80532c5813
Timestamp: 1705397558 Timestamp [UCT]: 2024-01-16 09:32:38 Age [y:d:h:m:s]: 01:296:10:49:45
Block: 936478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470688 RingCT/type: yes/0
Extra: 0106740e9f3fd9fb5cf2b567712f9538663599e44f48c211a006222d80532c581302110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 111341bf7e898c380f6f813d4c24e19955d78049a1cfef11df0dc3df95ccf716 0.600000000000 1394506 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 936488, "vin": [ { "gen": { "height": 936478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "111341bf7e898c380f6f813d4c24e19955d78049a1cfef11df0dc3df95ccf716" } } ], "extra": [ 1, 6, 116, 14, 159, 63, 217, 251, 92, 242, 181, 103, 113, 47, 149, 56, 102, 53, 153, 228, 79, 72, 194, 17, 160, 6, 34, 45, 128, 83, 44, 88, 19, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8