Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1dfdd07c7883ae8da4d205221b78251d183b00f7d0c43b15121e024d180f142

Tx prefix hash: 21ebd2206801e5a4d4f8794360f0e96698e91235fe0ed9838bcd39e0b739f2f6
Tx public key: e6795136930047e8178d5baf257e86eabb9c486e40edb18b545c6116e2664905
Timestamp: 1581650864 Timestamp [UCT]: 2020-02-14 03:27:44 Age [y:d:h:m:s]: 04:290:09:00:46
Block: 64614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099657 RingCT/type: yes/0
Extra: 01e6795136930047e8178d5baf257e86eabb9c486e40edb18b545c6116e26649050211000000048a2ee0d9000000000000000000

1 output(s) for total of 374.893410610000 dcy

stealth address amount amount idx
00: d3b7ab9711c784a7f3f4ea6535497028482cb3875bc639bade46c9ea6de2946d 374.893410610000 119190 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": 64624, "vin": [ { "gen": { "height": 64614 } } ], "vout": [ { "amount": 374893410610, "target": { "key": "d3b7ab9711c784a7f3f4ea6535497028482cb3875bc639bade46c9ea6de2946d" } } ], "extra": [ 1, 230, 121, 81, 54, 147, 0, 71, 232, 23, 141, 91, 175, 37, 126, 134, 234, 187, 156, 72, 110, 64, 237, 177, 139, 84, 92, 97, 22, 226, 102, 73, 5, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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