Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8429feb87d83acda67a05d7c5ef642cc6dcf2dcc8f8e0d8b2248c13832051514

Tx prefix hash: 046e880557c500acb5cb986ee2907fde33c6403bfd71209022884305a78aa9b4
Tx public key: bb503b3d0c90c592b09552c4c63736394a4ff5b4cb56a74103f3dce774ff2c89
Timestamp: 1735985551 Timestamp [UCT]: 2025-01-04 10:12:31 Age [y:d:h:m:s]: 00:086:23:26:24
Block: 1189957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61926 RingCT/type: yes/0
Extra: 01bb503b3d0c90c592b09552c4c63736394a4ff5b4cb56a74103f3dce774ff2c890211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e092f1384e3eb7ade8a2f9bf92fdd5bb0afb68cce33883fe2ee84f7de7d6fa5 0.600000000000 1676472 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": 1189967, "vin": [ { "gen": { "height": 1189957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e092f1384e3eb7ade8a2f9bf92fdd5bb0afb68cce33883fe2ee84f7de7d6fa5" } } ], "extra": [ 1, 187, 80, 59, 61, 12, 144, 197, 146, 176, 149, 82, 196, 198, 55, 54, 57, 74, 79, 245, 180, 203, 86, 167, 65, 3, 243, 220, 231, 116, 255, 44, 137, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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