Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa42df9cdea074034a763a165bf8027af27f696d513db7ec6c4f725c3a653011

Tx prefix hash: 66a15a1bfb08bb90590913c0c2d94a2503cbabadac06e4fdfc74ffe27c2fffc0
Tx public key: 75ef325032c78333c70f5c1f717db7867f09a0f9e18a16276415a1da709a1720
Timestamp: 1635391466 Timestamp [UCT]: 2021-10-28 03:24:26 Age [y:d:h:m:s]: 03:138:09:02:04
Block: 361965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877164 RingCT/type: yes/0
Extra: 0175ef325032c78333c70f5c1f717db7867f09a0f9e18a16276415a1da709a17200211000000017397a119000000000000000000

1 output(s) for total of 38.785340147000 dcy

stealth address amount amount idx
00: c07e35cb48f666b6412b3c514e4d9c47f61e03a783a8d5615c651e66bf523eaa 38.785340147000 736197 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": 361975, "vin": [ { "gen": { "height": 361965 } } ], "vout": [ { "amount": 38785340147, "target": { "key": "c07e35cb48f666b6412b3c514e4d9c47f61e03a783a8d5615c651e66bf523eaa" } } ], "extra": [ 1, 117, 239, 50, 80, 50, 199, 131, 51, 199, 15, 92, 31, 113, 125, 183, 134, 127, 9, 160, 249, 225, 138, 22, 39, 100, 21, 161, 218, 112, 154, 23, 32, 2, 17, 0, 0, 0, 1, 115, 151, 161, 25, 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