Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc900a8edf3cf31306d332084330d0df0d244e2919b465f35370689a13d30610

Tx prefix hash: fcb5d6309dab73991ac7c7a040954bfb3d3fab6b76cd40333e2717c8148e1014
Tx public key: 88bd0fe17e6ec15de43e6fd8cb5e226513b0b00d8048c1269ce167047b3d34c3
Timestamp: 1715581065 Timestamp [UCT]: 2024-05-13 06:17:45 Age [y:d:h:m:s]: 00:340:11:42:11
Block: 1020946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243360 RingCT/type: yes/0
Extra: 0188bd0fe17e6ec15de43e6fd8cb5e226513b0b00d8048c1269ce167047b3d34c30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75cbe6f392aa69af1b33c1343207f99a93a23ff679c6beeec734383fd797f04c 0.600000000000 1485085 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": 1020956, "vin": [ { "gen": { "height": 1020946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75cbe6f392aa69af1b33c1343207f99a93a23ff679c6beeec734383fd797f04c" } } ], "extra": [ 1, 136, 189, 15, 225, 126, 110, 193, 93, 228, 62, 111, 216, 203, 94, 34, 101, 19, 176, 176, 13, 128, 72, 193, 38, 156, 225, 103, 4, 123, 61, 52, 195, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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