Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64fd69dad11b80de00dc46cf81204bab6c2feb1b1921f08d14ea860067655b0

Tx prefix hash: 2645491c64626d35e4cb30561884b18b50450373cdf3c65a4f8a10084ba8e09a
Tx public key: 9c5c8bdf13aff90ccc36ec7a7a3ba57cb5d8089e1c3ab74954a8a69438771067
Timestamp: 1580571113 Timestamp [UCT]: 2020-02-01 15:31:53 Age [y:d:h:m:s]: 05:277:14:22:42
Block: 56718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1347869 RingCT/type: yes/0
Extra: 019c5c8bdf13aff90ccc36ec7a7a3ba57cb5d8089e1c3ab74954a8a69438771067021100000002dcee4b4d000000000000000000

1 output(s) for total of 398.171842118000 dcy

stealth address amount amount idx
00: 0b04a7d3f04ebeab2bf5be348564ae1feb1f164bfb6f13e03d5ea241a0c0fb6d 398.171842118000 104521 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": 56728, "vin": [ { "gen": { "height": 56718 } } ], "vout": [ { "amount": 398171842118, "target": { "key": "0b04a7d3f04ebeab2bf5be348564ae1feb1f164bfb6f13e03d5ea241a0c0fb6d" } } ], "extra": [ 1, 156, 92, 139, 223, 19, 175, 249, 12, 204, 54, 236, 122, 122, 59, 165, 124, 181, 216, 8, 158, 28, 58, 183, 73, 84, 168, 166, 148, 56, 119, 16, 103, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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