Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f87a9ad0ddaf145fec5d90eb551771248e236839e9c9f929d94da9aaaeac97

Tx prefix hash: 2fd141f0df0a1225707dcb926a9fc6fe77e4e98a33f64f3382fc98bfb2e0a278
Tx public key: 2cebe3ffe9f201ec9ade6a4371c8dc720143e08f83204f295c4248b87de90f6d
Timestamp: 1737374223 Timestamp [UCT]: 2025-01-20 11:57:03 Age [y:d:h:m:s]: 00:149:04:48:44
Block: 1201402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106377 RingCT/type: yes/0
Extra: 012cebe3ffe9f201ec9ade6a4371c8dc720143e08f83204f295c4248b87de90f6d0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49cbc8cece36ed947c4bdd6b190a06fce23d524f5d5a45fb25bc1321def4af8 0.600000000000 1688053 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": 1201412, "vin": [ { "gen": { "height": 1201402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49cbc8cece36ed947c4bdd6b190a06fce23d524f5d5a45fb25bc1321def4af8" } } ], "extra": [ 1, 44, 235, 227, 255, 233, 242, 1, 236, 154, 222, 106, 67, 113, 200, 220, 114, 1, 67, 224, 143, 131, 32, 79, 41, 92, 66, 72, 184, 125, 233, 15, 109, 2, 17, 0, 0, 0, 7, 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