Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ad86be1d137086daf19114bfc19c20b9274775ae44c179c15655abcd9fd68c0

Tx prefix hash: cf1a502636afbee5cd8ed1db130a873479fe9b94e764368c7836944ae5998479
Tx public key: 3fe7660fb38c1364067f856f918d259ce50971c95fde0bd9afa2c4b3a5a5ae5d
Timestamp: 1706798774 Timestamp [UCT]: 2024-02-01 14:46:14 Age [y:d:h:m:s]: 01:049:10:55:00
Block: 948090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296414 RingCT/type: yes/0
Extra: 013fe7660fb38c1364067f856f918d259ce50971c95fde0bd9afa2c4b3a5a5ae5d02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6852e7585e14d2dde8434c430f004b900b5c57768546c7e3d71aae43cdb01cd1 0.600000000000 1406462 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": 948100, "vin": [ { "gen": { "height": 948090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6852e7585e14d2dde8434c430f004b900b5c57768546c7e3d71aae43cdb01cd1" } } ], "extra": [ 1, 63, 231, 102, 15, 179, 140, 19, 100, 6, 127, 133, 111, 145, 141, 37, 156, 229, 9, 113, 201, 95, 222, 11, 217, 175, 162, 196, 179, 165, 165, 174, 93, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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