Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc878334f0e5eeaeb85a8a3af940d3b170c996cf0719f8c88c15a259bbfd86d

Tx prefix hash: fc0d4e536ee5cbcabc2cf23702cc60e8a85d9f1c8b4effc301ecf8acec6375e3
Tx public key: ea0e231e135a1bda24e8719c4d8ac184c92f86c9ee501ea367bb059665422d4e
Timestamp: 1733589615 Timestamp [UCT]: 2024-12-07 16:40:15 Age [y:d:h:m:s]: 00:117:17:39:15
Block: 1170116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83950 RingCT/type: yes/0
Extra: 01ea0e231e135a1bda24e8719c4d8ac184c92f86c9ee501ea367bb059665422d4e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b6d1e8e3e3fb67409587f88c8642bcefe7d38468df0cb70329205469376117 0.600000000000 1655845 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": 1170126, "vin": [ { "gen": { "height": 1170116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b6d1e8e3e3fb67409587f88c8642bcefe7d38468df0cb70329205469376117" } } ], "extra": [ 1, 234, 14, 35, 30, 19, 90, 27, 218, 36, 232, 113, 156, 77, 138, 193, 132, 201, 47, 134, 201, 238, 80, 30, 163, 103, 187, 5, 150, 101, 66, 45, 78, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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