Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c4481ef9e5c866907d447a17e7299527fc485893545eb87a015fa5b96164b0

Tx prefix hash: e1d13ef2213259c0e4c11a98db6f0ad89e54352616d1e742ebc6db20841ec4fa
Tx public key: 5ae3b12a556b6c3319d6a13ec529a6e273cd1d01f124a1930e3ba72ee03c78b3
Timestamp: 1702812469 Timestamp [UCT]: 2023-12-17 11:27:49 Age [y:d:h:m:s]: 01:123:10:20:26
Block: 915065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349363 RingCT/type: yes/0
Extra: 015ae3b12a556b6c3319d6a13ec529a6e273cd1d01f124a1930e3ba72ee03c78b302110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73210924178282f42e2d3e534fc24fa002f310394c9827dbad3a43aa2f37255c 0.600000000000 1372445 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": 915075, "vin": [ { "gen": { "height": 915065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73210924178282f42e2d3e534fc24fa002f310394c9827dbad3a43aa2f37255c" } } ], "extra": [ 1, 90, 227, 177, 42, 85, 107, 108, 51, 25, 214, 161, 62, 197, 41, 166, 226, 115, 205, 29, 1, 241, 36, 161, 147, 14, 59, 167, 46, 224, 60, 120, 179, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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