Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2dd099ebc697dabe8319d9a194bfe39d7ca4311f5857440469998a550908a87

Tx prefix hash: 0a17d6ef7831388277c523bb972ce6d1917210926119baf84eb4015a0f4218b6
Tx public key: 649a4fa0fb1a752074f30a05d8790cc6dcd8cf1a0775bdcd9cfe8e15a294ef2e
Timestamp: 1583236014 Timestamp [UCT]: 2020-03-03 11:46:54 Age [y:d:h:m:s]: 04:247:20:23:50
Block: 75388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1071575 RingCT/type: yes/0
Extra: 01649a4fa0fb1a752074f30a05d8790cc6dcd8cf1a0775bdcd9cfe8e15a294ef2e02110000000756c366d3000000000000000000

1 output(s) for total of 345.309922223000 dcy

stealth address amount amount idx
00: 652178a6c3ee0dfe5f83b3739ab662ad1ede2a33ad7463589d140fc08ee8a9cf 345.309922223000 139325 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": 75398, "vin": [ { "gen": { "height": 75388 } } ], "vout": [ { "amount": 345309922223, "target": { "key": "652178a6c3ee0dfe5f83b3739ab662ad1ede2a33ad7463589d140fc08ee8a9cf" } } ], "extra": [ 1, 100, 154, 79, 160, 251, 26, 117, 32, 116, 243, 10, 5, 216, 121, 12, 198, 220, 216, 207, 26, 7, 117, 189, 205, 156, 254, 142, 21, 162, 148, 239, 46, 2, 17, 0, 0, 0, 7, 86, 195, 102, 211, 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