Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744bc5e72fefdc4c73074167efa10e550bcc2b89e3e9f44ffc8d9b09e9eeaab4

Tx prefix hash: b4254775c1a0b132d4128be166154f435f05261abfc49ee5005123eb9be592d6
Tx public key: dde605cb0823ec815592f223a1f76698a5a6bb7d9cd9e2375ad1bef269288c8e
Timestamp: 1674214037 Timestamp [UCT]: 2023-01-20 11:27:17 Age [y:d:h:m:s]: 02:095:03:28:30
Block: 678836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589667 RingCT/type: yes/0
Extra: 01dde605cb0823ec815592f223a1f76698a5a6bb7d9cd9e2375ad1bef269288c8e0211000000015029cbac000000000000000000

1 output(s) for total of 3.457279397000 dcy

stealth address amount amount idx
00: 98ba973ae4e1646ef0dbf6fd02abccfd3cd53ba6eee1f42e253035fd8df2ef18 3.457279397000 1120781 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": 678846, "vin": [ { "gen": { "height": 678836 } } ], "vout": [ { "amount": 3457279397, "target": { "key": "98ba973ae4e1646ef0dbf6fd02abccfd3cd53ba6eee1f42e253035fd8df2ef18" } } ], "extra": [ 1, 221, 230, 5, 203, 8, 35, 236, 129, 85, 146, 242, 35, 161, 247, 102, 152, 165, 166, 187, 125, 156, 217, 226, 55, 90, 209, 190, 242, 105, 40, 140, 142, 2, 17, 0, 0, 0, 1, 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