Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199f1496ef5e6bfae66a0ff4e10d6a4fee06725457bfa5926dcd588a55fdbfd5

Tx prefix hash: 701511b1ebd018eaa358827c6d2dab77b07d8bfd3ea65bbc589ec87d72ff90de
Tx public key: 83c5b58acaf01ed13ff47664381402e5b960395ff7cb6df1d0a0c9c315d5fee3
Timestamp: 1681975804 Timestamp [UCT]: 2023-04-20 07:30:04 Age [y:d:h:m:s]: 01:356:08:43:07
Block: 742556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515971 RingCT/type: yes/0
Extra: 0183c5b58acaf01ed13ff47664381402e5b960395ff7cb6df1d0a0c9c315d5fee30211000000045029cbac000000000000000000

1 output(s) for total of 2.126199131000 dcy

stealth address amount amount idx
00: 15276dba85e5c7594df479240ebdc2e02f483aa63d59aeb46770dea68b7a9b55 2.126199131000 1189531 of 0

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": 742566, "vin": [ { "gen": { "height": 742556 } } ], "vout": [ { "amount": 2126199131, "target": { "key": "15276dba85e5c7594df479240ebdc2e02f483aa63d59aeb46770dea68b7a9b55" } } ], "extra": [ 1, 131, 197, 181, 138, 202, 240, 30, 209, 63, 244, 118, 100, 56, 20, 2, 229, 185, 96, 57, 95, 247, 203, 109, 241, 208, 160, 201, 195, 21, 213, 254, 227, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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