Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55946aa410f96572a8e125edfe806b12a1797a70c526d32bee3eb8370423442d

Tx prefix hash: 824d2f4590b096b6d8ce18117273dd6d151715b705c406f4cb7c4a26c7878d20
Tx public key: 02f9e30554a42d43db367b43e44d1ce7126332367188b2f6162c564a83ed6fdc
Timestamp: 1681979876 Timestamp [UCT]: 2023-04-20 08:37:56 Age [y:d:h:m:s]: 02:047:13:04:10
Block: 742592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556161 RingCT/type: yes/0
Extra: 0102f9e30554a42d43db367b43e44d1ce7126332367188b2f6162c564a83ed6fdc021100000005b3164c24000000000000000000

1 output(s) for total of 2.125615231000 dcy

stealth address amount amount idx
00: 45d7035c2d45576580aecf0fe69f3cb1d95d8ead8abffb7575e638cb404f3491 2.125615231000 1189567 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": 742602, "vin": [ { "gen": { "height": 742592 } } ], "vout": [ { "amount": 2125615231, "target": { "key": "45d7035c2d45576580aecf0fe69f3cb1d95d8ead8abffb7575e638cb404f3491" } } ], "extra": [ 1, 2, 249, 227, 5, 84, 164, 45, 67, 219, 54, 123, 67, 228, 77, 28, 231, 18, 99, 50, 54, 113, 136, 178, 246, 22, 44, 86, 74, 131, 237, 111, 220, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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