Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b210384d328bb6e473e6ddb9d9a5dd67b3e7b7416239891a17f20e4128de594f

Tx prefix hash: 5f789891c667caf10bf065a5ac9d89f6fc62fd8e6ada38cb99a1585551ab6c2b
Tx public key: 48466f23ac95dae36aa2a8bccb8dbdaa3364f06e245a481a2617ba5f08b538aa
Timestamp: 1722864173 Timestamp [UCT]: 2024-08-05 13:22:53 Age [y:d:h:m:s]: 00:170:09:51:37
Block: 1081296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121872 RingCT/type: yes/0
Extra: 0148466f23ac95dae36aa2a8bccb8dbdaa3364f06e245a481a2617ba5f08b538aa021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f5b0116181faa4261d8f88e221a4bebcbd2bced3894915724fec951d8935d3a 0.600000000000 1554987 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": 1081306, "vin": [ { "gen": { "height": 1081296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f5b0116181faa4261d8f88e221a4bebcbd2bced3894915724fec951d8935d3a" } } ], "extra": [ 1, 72, 70, 111, 35, 172, 149, 218, 227, 106, 162, 168, 188, 203, 141, 189, 170, 51, 100, 240, 110, 36, 90, 72, 26, 38, 23, 186, 95, 8, 181, 56, 170, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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