Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79938f17e3a7059c9517c9bb5893dbf8fb53ea86acd215f63f5346fe6040fc0a

Tx prefix hash: 89cccb44a1660d589b4f5a1724307cd19934dbdca335453b1396fd1f57c61571
Tx public key: 516019009dc7c8024ca5e7d82791f1aed47a2107eb39c77ecf6a2f508a6e6264
Timestamp: 1719402543 Timestamp [UCT]: 2024-06-26 11:49:03 Age [y:d:h:m:s]: 00:294:10:43:48
Block: 1052593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210409 RingCT/type: yes/0
Extra: 01516019009dc7c8024ca5e7d82791f1aed47a2107eb39c77ecf6a2f508a6e62640211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d0cc23fdd88743e66ee7ed54e52926f6a366855a640f4860d6aa3fe06619e3 0.600000000000 1522924 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": 1052603, "vin": [ { "gen": { "height": 1052593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d0cc23fdd88743e66ee7ed54e52926f6a366855a640f4860d6aa3fe06619e3" } } ], "extra": [ 1, 81, 96, 25, 0, 157, 199, 200, 2, 76, 165, 231, 216, 39, 145, 241, 174, 212, 122, 33, 7, 235, 57, 199, 126, 207, 106, 47, 80, 138, 110, 98, 100, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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