Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88290f7d9489730756cd0c18beeb7001dad70b5361941d06797187e55469e6ca

Tx prefix hash: 5726c704ac24bdb823af905d638283b2d645e743b7fb3bff81361c116f4f3036
Tx public key: cd1575805e540f4e417a330f351b8d241bce14c26bca00e17112e0c4a83bbf68
Timestamp: 1702425810 Timestamp [UCT]: 2023-12-13 00:03:30 Age [y:d:h:m:s]: 01:107:19:00:31
Block: 911881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338145 RingCT/type: yes/0
Extra: 01cd1575805e540f4e417a330f351b8d241bce14c26bca00e17112e0c4a83bbf6802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fa6c43d5531d6900230516f8cdb5197e344c583dfb4a3a2c352218d092c3b5c 0.600000000000 1369097 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": 911891, "vin": [ { "gen": { "height": 911881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fa6c43d5531d6900230516f8cdb5197e344c583dfb4a3a2c352218d092c3b5c" } } ], "extra": [ 1, 205, 21, 117, 128, 94, 84, 15, 78, 65, 122, 51, 15, 53, 27, 141, 36, 27, 206, 20, 194, 107, 202, 0, 225, 113, 18, 224, 196, 168, 59, 191, 104, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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