Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45f7aa03d2e09602f5a7745e764fd2ce604bf64c1061cf2cddd8d60deb4694e

Tx prefix hash: fdbca103b6c0f7b6926b3ba4eccf82534c8f624695d65141c1fd6578c69a66f4
Tx public key: 5851b70b03d15623cc937dda77341384d6025e26a931248f8a8196edf699352f
Timestamp: 1697125073 Timestamp [UCT]: 2023-10-12 15:37:53 Age [y:d:h:m:s]: 01:135:05:24:16
Block: 868129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357623 RingCT/type: yes/0
Extra: 015851b70b03d15623cc937dda77341384d6025e26a931248f8a8196edf699352f02110000000b4b8f5122000000000000000000

1 output(s) for total of 0.815695893000 dcy

stealth address amount amount idx
00: bae036c1e806f49194d8b3df56d4094c1948c0e09da0c2190ad1971b28aa31e9 0.815695893000 1322900 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": 868139, "vin": [ { "gen": { "height": 868129 } } ], "vout": [ { "amount": 815695893, "target": { "key": "bae036c1e806f49194d8b3df56d4094c1948c0e09da0c2190ad1971b28aa31e9" } } ], "extra": [ 1, 88, 81, 183, 11, 3, 209, 86, 35, 204, 147, 125, 218, 119, 52, 19, 132, 214, 2, 94, 38, 169, 49, 36, 143, 138, 129, 150, 237, 246, 153, 53, 47, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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