Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32b6f173f86715a3a8ab60d11fe3322c5ad60e0fc765b18b925a24dee13b2e16

Tx prefix hash: 6b18bfa92b0edae8aeaaf5b54f173e30ff30feb0cd45d41ac3a7681ff751221e
Tx public key: 9422015311472009c275939ff3abebee748530ed9340e08d3f3c624e39ca9a1e
Timestamp: 1583225172 Timestamp [UCT]: 2020-03-03 08:46:12 Age [y:d:h:m:s]: 04:247:23:44:55
Block: 75188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1071783 RingCT/type: yes/0
Extra: 019422015311472009c275939ff3abebee748530ed9340e08d3f3c624e39ca9a1e02110000000e8a2ee0d9000000000000000000

1 output(s) for total of 345.849177560000 dcy

stealth address amount amount idx
00: 3590f35bdc34a6d5ebeacad9d2b941b1c265a330cf50b73f7fc09e0a4f0556af 345.849177560000 139073 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": 75198, "vin": [ { "gen": { "height": 75188 } } ], "vout": [ { "amount": 345849177560, "target": { "key": "3590f35bdc34a6d5ebeacad9d2b941b1c265a330cf50b73f7fc09e0a4f0556af" } } ], "extra": [ 1, 148, 34, 1, 83, 17, 71, 32, 9, 194, 117, 147, 159, 243, 171, 235, 238, 116, 133, 48, 237, 147, 64, 224, 141, 63, 60, 98, 78, 57, 202, 154, 30, 2, 17, 0, 0, 0, 14, 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