Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aadc1b04f57533f7c76556fc65995d54e0b5c1d22161327143875332576d40cc

Tx prefix hash: 62c05f2754c300209a07733759ec2cfbd363458a539b9f5f6a94bbb4fe9a0590
Tx public key: 7935abded51265e7fb5b65ad1ab2ba0571ba0a7d44ae3da2fb9b8bcbe03cbe40
Timestamp: 1705159690 Timestamp [UCT]: 2024-01-13 15:28:10 Age [y:d:h:m:s]: 01:066:07:59:00
Block: 934506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308526 RingCT/type: yes/0
Extra: 017935abded51265e7fb5b65ad1ab2ba0571ba0a7d44ae3da2fb9b8bcbe03cbe400211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 411a18a7b42f7dd4a523c52c58d76c389edd855e203c21e040e4e58b93b35419 0.600000000000 1392520 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": 934516, "vin": [ { "gen": { "height": 934506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "411a18a7b42f7dd4a523c52c58d76c389edd855e203c21e040e4e58b93b35419" } } ], "extra": [ 1, 121, 53, 171, 222, 213, 18, 101, 231, 251, 91, 101, 173, 26, 178, 186, 5, 113, 186, 10, 125, 68, 174, 61, 162, 251, 155, 139, 203, 224, 60, 190, 64, 2, 17, 0, 0, 0, 1, 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