Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349f86302908e7c99a2ab3571dd232f52897fcd4c9d0e17642e69f220af75d72

Tx prefix hash: f557dd0a7f59198f53fd311dc8a1c0fc765827b6934617dc83c57e7bc707c7cd
Tx public key: 8b56f2f05e835e3792e3ed485500daefc39c3de860eb707c652816e1a9c55365
Timestamp: 1714793080 Timestamp [UCT]: 2024-05-04 03:24:40 Age [y:d:h:m:s]: 00:140:10:35:20
Block: 1014393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100597 RingCT/type: yes/0
Extra: 018b56f2f05e835e3792e3ed485500daefc39c3de860eb707c652816e1a9c5536502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ec6a51d10a45c38d4e740ca5aa5e00ec129b75c9d28841fe0e7fed96875c993 0.600000000000 1477474 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": 1014403, "vin": [ { "gen": { "height": 1014393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ec6a51d10a45c38d4e740ca5aa5e00ec129b75c9d28841fe0e7fed96875c993" } } ], "extra": [ 1, 139, 86, 242, 240, 94, 131, 94, 55, 146, 227, 237, 72, 85, 0, 218, 239, 195, 156, 61, 232, 96, 235, 112, 124, 101, 40, 22, 225, 169, 197, 83, 101, 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