Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b0364052c41ec5608e65064131114d023ec3941d69c8d0c869fc27be59bf6a1

Tx prefix hash: 1c0b409e2192e6ea5e70a9416e9c93bd5777c2ca1782eac917f0778517111c8d
Tx public key: 6acc9ea47683e27b13bf409b8ff4c00607cf3bffcb3e7b3356715bb3f2099b19
Timestamp: 1718278508 Timestamp [UCT]: 2024-06-13 11:35:08 Age [y:d:h:m:s]: 00:337:08:45:57
Block: 1043287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241113 RingCT/type: yes/0
Extra: 016acc9ea47683e27b13bf409b8ff4c00607cf3bffcb3e7b3356715bb3f2099b190211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d60a8b365b8240ebbab95877fdb9fb1986415f8f919fbcacc125f74c130ee5 0.600000000000 1512404 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": 1043297, "vin": [ { "gen": { "height": 1043287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d60a8b365b8240ebbab95877fdb9fb1986415f8f919fbcacc125f74c130ee5" } } ], "extra": [ 1, 106, 204, 158, 164, 118, 131, 226, 123, 19, 191, 64, 155, 143, 244, 192, 6, 7, 207, 59, 255, 203, 62, 123, 51, 86, 113, 91, 179, 242, 9, 155, 25, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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