Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 534bd2c45076385447dde85f73c7e740bb673a14dabfa75f59443db51ef13ab1

Tx prefix hash: b079580fba2c732d4076f79c05e6b09a5515988f71803a776385cef511dfe78a
Tx public key: a37b51dbb977a7dc40a2b1c55079e8694fb6dad4a9b3ac8d2a50a2999a2ec82c
Timestamp: 1718909852 Timestamp [UCT]: 2024-06-20 18:57:32 Age [y:d:h:m:s]: 00:281:02:54:42
Block: 1048513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200881 RingCT/type: yes/0
Extra: 01a37b51dbb977a7dc40a2b1c55079e8694fb6dad4a9b3ac8d2a50a2999a2ec82c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 247f7a87043938241b8c1715f1a806a4ca2908889abe0f5eaf1f08e2541fa6fc 0.600000000000 1518598 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": 1048523, "vin": [ { "gen": { "height": 1048513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "247f7a87043938241b8c1715f1a806a4ca2908889abe0f5eaf1f08e2541fa6fc" } } ], "extra": [ 1, 163, 123, 81, 219, 185, 119, 167, 220, 64, 162, 177, 197, 80, 121, 232, 105, 79, 182, 218, 212, 169, 179, 172, 141, 42, 80, 162, 153, 154, 46, 200, 44, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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