Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec849587470523da3a88edc5302aa579ff49174f9ecd682d803336ac367c1dd

Tx prefix hash: 1f78e2fb8472a72db4b9f41fc83bf3c7b7f4f1d80c7149a9040df551ca3a862f
Tx public key: 83c03e636b587e8b0dd595152f7886e71abbcd7b522b1d9ff80b29d30cfb09a7
Timestamp: 1721208922 Timestamp [UCT]: 2024-07-17 09:35:22 Age [y:d:h:m:s]: 00:193:00:25:19
Block: 1067591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138046 RingCT/type: yes/0
Extra: 0183c03e636b587e8b0dd595152f7886e71abbcd7b522b1d9ff80b29d30cfb09a702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c0a0994443b5c276891e412070f05d333e343bd34c62ddc4a819ec493c54e2e 0.600000000000 1538438 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": 1067601, "vin": [ { "gen": { "height": 1067591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c0a0994443b5c276891e412070f05d333e343bd34c62ddc4a819ec493c54e2e" } } ], "extra": [ 1, 131, 192, 62, 99, 107, 88, 126, 139, 13, 213, 149, 21, 47, 120, 134, 231, 26, 187, 205, 123, 82, 43, 29, 159, 248, 11, 41, 211, 12, 251, 9, 167, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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