Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 405df79e21eb44b29b1671f522a663ea76ecb44547e6e941ca67d69a7a6465cf

Tx prefix hash: 6e5f4559b36df0f864f14767f85e6bf578201ea056e5045a64ba002b0a662c5a
Tx public key: 33a9f28c68d18fc10b66dd70824602c3483349028e3d2d720cfb4ba1ba0aa794
Timestamp: 1686452857 Timestamp [UCT]: 2023-06-11 03:07:37 Age [y:d:h:m:s]: 01:223:00:12:12
Block: 779697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420741 RingCT/type: yes/0
Extra: 0133a9f28c68d18fc10b66dd70824602c3483349028e3d2d720cfb4ba1ba0aa7940211000000024b8f5122000000000000000000

1 output(s) for total of 1.601549370000 dcy

stealth address amount amount idx
00: d2366db16b22062909e21b6c857f398ae4cace872f6f7a1456592615d3d331f1 1.601549370000 1229368 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": 779707, "vin": [ { "gen": { "height": 779697 } } ], "vout": [ { "amount": 1601549370, "target": { "key": "d2366db16b22062909e21b6c857f398ae4cace872f6f7a1456592615d3d331f1" } } ], "extra": [ 1, 51, 169, 242, 140, 104, 209, 143, 193, 11, 102, 221, 112, 130, 70, 2, 195, 72, 51, 73, 2, 142, 61, 45, 114, 12, 251, 75, 161, 186, 10, 167, 148, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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