Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d2ec14e2f57c69ac5e6875f69fecc1d108248810a29179de341456c2817b289

Tx prefix hash: 9184d59531c280e279615b49ad7a57879a6dbe1fb596d66ed29d8931184ee562
Tx public key: 24b1ffeb30b73b6dc7fa18e5958a51e9d1bded1a281be19845774928ee99ae2c
Timestamp: 1577633210 Timestamp [UCT]: 2019-12-29 15:26:50 Age [y:d:h:m:s]: 05:157:12:45:43
Block: 34398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1262405 RingCT/type: yes/0
Extra: 0124b1ffeb30b73b6dc7fa18e5958a51e9d1bded1a281be19845774928ee99ae2c0211000000034ac5aa02000000000000000000

1 output(s) for total of 472.091305982000 dcy

stealth address amount amount idx
00: c4337e29ecfba1fca782f05fdd540aa4d624aeb87fea93668726ba14238eefe1 472.091305982000 57892 of 0

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": 34408, "vin": [ { "gen": { "height": 34398 } } ], "vout": [ { "amount": 472091305982, "target": { "key": "c4337e29ecfba1fca782f05fdd540aa4d624aeb87fea93668726ba14238eefe1" } } ], "extra": [ 1, 36, 177, 255, 235, 48, 183, 59, 109, 199, 250, 24, 229, 149, 138, 81, 233, 209, 189, 237, 26, 40, 27, 225, 152, 69, 119, 73, 40, 238, 153, 174, 44, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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