Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d43278022b3ed3c2a0d098caf9f0ff43ed9d2bb39ee5680b1dfff7ab2fb488

Tx prefix hash: a651b3a1808d827a36cc85780e6a99c2e4df1f26232efeff2d11ad431e8d2a20
Tx public key: 633b8d2dec5d40e9731341f626cc355735794c5612e23104a96202c2eba07ff8
Timestamp: 1739801844 Timestamp [UCT]: 2025-02-17 14:17:24 Age [y:d:h:m:s]: 00:344:08:00:23
Block: 1221254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243781 RingCT/type: yes/0
Extra: 01633b8d2dec5d40e9731341f626cc355735794c5612e23104a96202c2eba07ff80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1f72c05f55069d92d1a1c7a8b191126c04fe1c14bf9c2dd7bb2addb3f23c93f 0.600000000000 1708099 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": 1221264, "vin": [ { "gen": { "height": 1221254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1f72c05f55069d92d1a1c7a8b191126c04fe1c14bf9c2dd7bb2addb3f23c93f" } } ], "extra": [ 1, 99, 59, 141, 45, 236, 93, 64, 233, 115, 19, 65, 246, 38, 204, 53, 87, 53, 121, 76, 86, 18, 226, 49, 4, 169, 98, 2, 194, 235, 160, 127, 248, 2, 17, 0, 0, 0, 3, 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