Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 465c1b73e509f5feca9ffd1305fefc38ded77c7ea889d6e4a84dfef74b7d3544

Tx prefix hash: 7f4b193ab90160ee4c058e5c7ac5943e8954765ea2d5e8a1e5c5ca849e51e47e
Tx public key: 682ffe34f93a9104e3e409c3398d7082f59321ff501843f852060eed51fa9a23
Timestamp: 1718494597 Timestamp [UCT]: 2024-06-15 23:36:37 Age [y:d:h:m:s]: 00:293:10:00:12
Block: 1045094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209659 RingCT/type: yes/0
Extra: 01682ffe34f93a9104e3e409c3398d7082f59321ff501843f852060eed51fa9a230211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4aafa0d0be9a70cdaa70a1414d983e7fec401f1ee64e1e65257aea95e42fcb8 0.600000000000 1514575 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": 1045104, "vin": [ { "gen": { "height": 1045094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4aafa0d0be9a70cdaa70a1414d983e7fec401f1ee64e1e65257aea95e42fcb8" } } ], "extra": [ 1, 104, 47, 254, 52, 249, 58, 145, 4, 227, 228, 9, 195, 57, 141, 112, 130, 245, 147, 33, 255, 80, 24, 67, 248, 82, 6, 14, 237, 81, 250, 154, 35, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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