Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 654b91f8c0d447f29306510fef93afa52ca49a242da89866b915bc1a93125f67

Tx prefix hash: 7189d6d47d8aa32cf2ad2c74ae6073513d7f99e3bece36aeeb54a825156f6485
Tx public key: c1d6a2c507fcf83c6b63a0f154e10830c23a3cfe7804e741fbc523c2b6363028
Timestamp: 1716560436 Timestamp [UCT]: 2024-05-24 14:20:36 Age [y:d:h:m:s]: 00:233:12:38:01
Block: 1029050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167121 RingCT/type: yes/0
Extra: 01c1d6a2c507fcf83c6b63a0f154e10830c23a3cfe7804e741fbc523c2b63630280211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99ef5bdf688a8ebec351a3a8e212fc4475cbf8ea9844fbb02b6820f65b58492f 0.600000000000 1497051 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": 1029060, "vin": [ { "gen": { "height": 1029050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99ef5bdf688a8ebec351a3a8e212fc4475cbf8ea9844fbb02b6820f65b58492f" } } ], "extra": [ 1, 193, 214, 162, 197, 7, 252, 248, 60, 107, 99, 160, 241, 84, 225, 8, 48, 194, 58, 60, 254, 120, 4, 231, 65, 251, 197, 35, 194, 182, 54, 48, 40, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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