Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 627ec9ee2b39328c138bf6c60104ec3db46769fd022f84a43c1985e2a7c1da98

Tx prefix hash: fd7415b8ae3df0ff028430652ce514e32965e9a246b8b75ad0690d4337e9ff39
Tx public key: b75a4f94465b3e8e4345bad92a04fb0b8d1485713adf5838e5118b4933ac58a5
Timestamp: 1736691477 Timestamp [UCT]: 2025-01-12 14:17:57 Age [y:d:h:m:s]: 00:093:07:36:45
Block: 1195797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66481 RingCT/type: yes/0
Extra: 01b75a4f94465b3e8e4345bad92a04fb0b8d1485713adf5838e5118b4933ac58a50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac2d8e957d6d8d3cace5a3057e4c1510ae91cc7420af925584e7364fba1538b9 0.600000000000 1682390 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": 1195807, "vin": [ { "gen": { "height": 1195797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac2d8e957d6d8d3cace5a3057e4c1510ae91cc7420af925584e7364fba1538b9" } } ], "extra": [ 1, 183, 90, 79, 148, 70, 91, 62, 142, 67, 69, 186, 217, 42, 4, 251, 11, 141, 20, 133, 113, 58, 223, 88, 56, 229, 17, 139, 73, 51, 172, 88, 165, 2, 17, 0, 0, 0, 1, 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