Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7eced6fcbedfb461b69067f7b6ad7b72b96e6d9e208b1d8848238dccf6d9f74

Tx prefix hash: 9342c76adf206bd5d30eced85af82f1e83acfc4a2f4a36ccba335fcb3f201cbb
Tx public key: 1354c801bbfbaeeb1e234ad5f8bb1ee643d115f5daca07156e05156618729a94
Timestamp: 1734402574 Timestamp [UCT]: 2024-12-17 02:29:34 Age [y:d:h:m:s]: 00:087:22:15:53
Block: 1176870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62616 RingCT/type: yes/0
Extra: 011354c801bbfbaeeb1e234ad5f8bb1ee643d115f5daca07156e05156618729a940211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01e676b3fb77d3c1c0174e50bc1294a37790cc04ec6c319a3836b4bd832d6753 0.600000000000 1663231 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": 1176880, "vin": [ { "gen": { "height": 1176870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01e676b3fb77d3c1c0174e50bc1294a37790cc04ec6c319a3836b4bd832d6753" } } ], "extra": [ 1, 19, 84, 200, 1, 187, 251, 174, 235, 30, 35, 74, 213, 248, 187, 30, 230, 67, 209, 21, 245, 218, 202, 7, 21, 110, 5, 21, 102, 24, 114, 154, 148, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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