Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583e48e1401881f9321651c63f239e14be8e93133a565cfc587b0aa76ef26f73

Tx prefix hash: 602ab777f7b8d3778ccb8da42ace563e641f4e4fab9a00fd0c23a8bf9e0df1f2
Tx public key: 35bd1a629420d05e0611084a1270051d91d7da28324a7ec63e5e92bacda6d5dc
Timestamp: 1711437551 Timestamp [UCT]: 2024-03-26 07:19:11 Age [y:d:h:m:s]: 01:229:14:15:11
Block: 986589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422762 RingCT/type: yes/0
Extra: 0135bd1a629420d05e0611084a1270051d91d7da28324a7ec63e5e92bacda6d5dc0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b1bb63c35bca12119dfded0acc8f5bac3e1fe58aed82cc6c72455a2345d0db9 0.600000000000 1446820 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": 986599, "vin": [ { "gen": { "height": 986589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b1bb63c35bca12119dfded0acc8f5bac3e1fe58aed82cc6c72455a2345d0db9" } } ], "extra": [ 1, 53, 189, 26, 98, 148, 32, 208, 94, 6, 17, 8, 74, 18, 112, 5, 29, 145, 215, 218, 40, 50, 74, 126, 198, 62, 94, 146, 186, 205, 166, 213, 220, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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