Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce974e1dbaf45e1a2294a303d22b7ce5c3386a4f5ffbc55c3c318022bc1bcfd

Tx prefix hash: d90610191000a49c7ad70d8eb632638fb25ab09deb625ffbc290a6684d71740c
Tx public key: f82208e49e86fa72e845bc435ff32abf213a6081c1a2c523e4b806f5f23921c8
Timestamp: 1729841504 Timestamp [UCT]: 2024-10-25 07:31:44 Age [y:d:h:m:s]: 00:162:01:23:08
Block: 1139106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115633 RingCT/type: yes/0
Extra: 01f82208e49e86fa72e845bc435ff32abf213a6081c1a2c523e4b806f5f23921c80211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e342afbf8f73dc35ae47f11362c8c52cb70f5caaedcf6e8807a6cd18acb6180 0.600000000000 1622869 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": 1139116, "vin": [ { "gen": { "height": 1139106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e342afbf8f73dc35ae47f11362c8c52cb70f5caaedcf6e8807a6cd18acb6180" } } ], "extra": [ 1, 248, 34, 8, 228, 158, 134, 250, 114, 232, 69, 188, 67, 95, 243, 42, 191, 33, 58, 96, 129, 193, 162, 197, 35, 228, 184, 6, 245, 242, 57, 33, 200, 2, 17, 0, 0, 0, 5, 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