Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d590f2e1e0fa333a25c1f509cbe0bf5d5a9f30d45c48dcf64f396bd12a5368b

Tx prefix hash: 2f8419c5dba5ad30fde99f12d57486d8f0112e3587db96ccd5c0ac8e5ea349fe
Tx public key: 37d5f75500b4eed375a1fe3f6fd30f175580c2d19745e4c453ac848d8b29965b
Timestamp: 1729275400 Timestamp [UCT]: 2024-10-18 18:16:40 Age [y:d:h:m:s]: 00:004:07:21:48
Block: 1134461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3048 RingCT/type: yes/0
Extra: 0137d5f75500b4eed375a1fe3f6fd30f175580c2d19745e4c453ac848d8b29965b0211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90bb12ae49b89aee2b00e5672a7a567f4647d075b2c6e3ea53146142e7922846 0.600000000000 1617768 of 15

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": 1134471, "vin": [ { "gen": { "height": 1134461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90bb12ae49b89aee2b00e5672a7a567f4647d075b2c6e3ea53146142e7922846" } } ], "extra": [ 1, 55, 213, 247, 85, 0, 180, 238, 211, 117, 161, 254, 63, 111, 211, 15, 23, 85, 128, 194, 209, 151, 69, 228, 196, 83, 172, 132, 141, 139, 41, 150, 91, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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