Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2024c16f4844aa618502e0cd5f380d7c9010141b611212cf4779d50f3f26b206

Tx prefix hash: bf2e906b185cf9b52f3c784b576ebd1c9a1d093c1d11964a548188d96814326e
Tx public key: c38acca191abdee39807e3ae826701cdb6cdfd1f9e7135f83e90b8176542fd75
Timestamp: 1719957393 Timestamp [UCT]: 2024-07-02 21:56:33 Age [y:d:h:m:s]: 00:324:17:54:18
Block: 1057195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232082 RingCT/type: yes/0
Extra: 01c38acca191abdee39807e3ae826701cdb6cdfd1f9e7135f83e90b8176542fd750211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fba0e69d7b33837de94e946a4501dfa5e163ee69af2c65c1644639a10368f17 0.600000000000 1527628 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": 1057205, "vin": [ { "gen": { "height": 1057195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fba0e69d7b33837de94e946a4501dfa5e163ee69af2c65c1644639a10368f17" } } ], "extra": [ 1, 195, 138, 204, 161, 145, 171, 222, 227, 152, 7, 227, 174, 130, 103, 1, 205, 182, 205, 253, 31, 158, 113, 53, 248, 62, 144, 184, 23, 101, 66, 253, 117, 2, 17, 0, 0, 0, 2, 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