Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a994b4ef3a7c45d57dde8727ec77a9767bc3b9331d47a78e17dfddbcbb922cf0

Tx prefix hash: 4d43d262e90c083e2c0985c4f31a517149f9e99b0c1bb02cfbed10a44c8120c8
Tx public key: e912517ef404b9f7171d0773aa143910cc93047d1b5eaab8e98b4ccf2d643bc0
Timestamp: 1577647102 Timestamp [UCT]: 2019-12-29 19:18:22 Age [y:d:h:m:s]: 05:093:18:03:15
Block: 34506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1216782 RingCT/type: yes/0
Extra: 01e912517ef404b9f7171d0773aa143910cc93047d1b5eaab8e98b4ccf2d643bc00211000000028a2ee0d9000000000000000000

1 output(s) for total of 471.702473466000 dcy

stealth address amount amount idx
00: 0298c73ab878d161bdb5c36e0e7a340c5d8fdf2ac7e800255c94a2415b5703a3 471.702473466000 58082 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": 34516, "vin": [ { "gen": { "height": 34506 } } ], "vout": [ { "amount": 471702473466, "target": { "key": "0298c73ab878d161bdb5c36e0e7a340c5d8fdf2ac7e800255c94a2415b5703a3" } } ], "extra": [ 1, 233, 18, 81, 126, 244, 4, 185, 247, 23, 29, 7, 115, 170, 20, 57, 16, 204, 147, 4, 125, 27, 94, 170, 184, 233, 139, 76, 207, 45, 100, 59, 192, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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