Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cae2f8fbc66bc262694c00b011a5840a98f3a4685aee8a9616c47864073370e

Tx prefix hash: 364537632fef78898be68d2d1df2ff9e64a05d90ff43af9dfc019d58261c3ab1
Tx public key: 1dec52c8c972653fbbf8a704e16948809c658be921a4bee3fe61cb9b3bf202cf
Timestamp: 1735761286 Timestamp [UCT]: 2025-01-01 19:54:46 Age [y:d:h:m:s]: 00:170:17:58:56
Block: 1188090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121703 RingCT/type: yes/0
Extra: 011dec52c8c972653fbbf8a704e16948809c658be921a4bee3fe61cb9b3bf202cf02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dec2e6b402c50f62b09d88fabb9c275e3d5d6470975eaed08a74deb57d4be90 0.600000000000 1674589 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": 1188100, "vin": [ { "gen": { "height": 1188090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dec2e6b402c50f62b09d88fabb9c275e3d5d6470975eaed08a74deb57d4be90" } } ], "extra": [ 1, 29, 236, 82, 200, 201, 114, 101, 63, 187, 248, 167, 4, 225, 105, 72, 128, 156, 101, 139, 233, 33, 164, 190, 227, 254, 97, 203, 155, 59, 242, 2, 207, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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