Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c545225729b3c4b6033361477527a411ba213e5eec42a0f3e716286445e10df7

Tx prefix hash: c0381ee070fbd29553928428d848e72d5d95871e68cb3db93755fef9138e21fb
Tx public key: 470ad10534e773a5c32ce94c0117270e1d052103f93f9b9f0ca4802981bd6c89
Timestamp: 1713514965 Timestamp [UCT]: 2024-04-19 08:22:45 Age [y:d:h:m:s]: 00:311:23:12:30
Block: 1003790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222991 RingCT/type: yes/0
Extra: 01470ad10534e773a5c32ce94c0117270e1d052103f93f9b9f0ca4802981bd6c890211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a08e8c4b46fa687f5f7f2ca56fbe55492e341ab4b43f15b629db3cc23fc4ff3f 0.600000000000 1464334 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": 1003800, "vin": [ { "gen": { "height": 1003790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a08e8c4b46fa687f5f7f2ca56fbe55492e341ab4b43f15b629db3cc23fc4ff3f" } } ], "extra": [ 1, 71, 10, 209, 5, 52, 231, 115, 165, 195, 44, 233, 76, 1, 23, 39, 14, 29, 5, 33, 3, 249, 63, 155, 159, 12, 164, 128, 41, 129, 189, 108, 137, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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