Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df10ff39cb28d19ef858f557172fd879b99d058e7c64e111c2a19a1d4a62bc99

Tx prefix hash: 18489878165c0a9b88aa2c071e8c52618cfb32f145f42df201e7239bcbdaa8e3
Tx public key: 451d0e065d7797b0bc1476d2ba65b7f4f2513135f09400a6d3799f89a63087db
Timestamp: 1680978410 Timestamp [UCT]: 2023-04-08 18:26:50 Age [y:d:h:m:s]: 02:002:02:20:34
Block: 734342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523601 RingCT/type: yes/0
Extra: 01451d0e065d7797b0bc1476d2ba65b7f4f2513135f09400a6d3799f89a63087db021100000001b3164c24000000000000000000

1 output(s) for total of 2.263707659000 dcy

stealth address amount amount idx
00: 6421316ee59d139fa68951125ea7f9d7691756f0e9560572c0aeade60a472f77 2.263707659000 1180533 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": 734352, "vin": [ { "gen": { "height": 734342 } } ], "vout": [ { "amount": 2263707659, "target": { "key": "6421316ee59d139fa68951125ea7f9d7691756f0e9560572c0aeade60a472f77" } } ], "extra": [ 1, 69, 29, 14, 6, 93, 119, 151, 176, 188, 20, 118, 210, 186, 101, 183, 244, 242, 81, 49, 53, 240, 148, 0, 166, 211, 121, 159, 137, 166, 48, 135, 219, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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