Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ba749e3bfd58e0351d3ae0f614e2eefe2c72fd84b29950ccfa509d7f86babf

Tx prefix hash: e6cc76f95c34770b44033bf8a9c716a247a2203837ae20d6a77e6289f327eaba
Tx public key: 0d21e2b3a3407193a0d7a452d05d03ef2c1f9c224da71e5fee4c4151ca37feae
Timestamp: 1696622374 Timestamp [UCT]: 2023-10-06 19:59:34 Age [y:d:h:m:s]: 01:181:09:03:41
Block: 863950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390659 RingCT/type: yes/0
Extra: 010d21e2b3a3407193a0d7a452d05d03ef2c1f9c224da71e5fee4c4151ca37feae021100000001faf35c9c000000000000000000

1 output(s) for total of 0.842122059000 dcy

stealth address amount amount idx
00: 0313c6a00b0d8bc95823a8095834aff7700b15ba8853e8bd422ce487bbf3c76c 0.842122059000 1318450 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": 863960, "vin": [ { "gen": { "height": 863950 } } ], "vout": [ { "amount": 842122059, "target": { "key": "0313c6a00b0d8bc95823a8095834aff7700b15ba8853e8bd422ce487bbf3c76c" } } ], "extra": [ 1, 13, 33, 226, 179, 163, 64, 113, 147, 160, 215, 164, 82, 208, 93, 3, 239, 44, 31, 156, 34, 77, 167, 30, 95, 238, 76, 65, 81, 202, 55, 254, 174, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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