Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b6f20ec605634366f7b048896393cb71045ef5d49b6fbfb5f4370299d9e35c5

Tx prefix hash: 9302cd6a1a7f8228fec5c46bf8612a02ee4b68bb5dfa9a07c290ab9ad437663d
Tx public key: cb946aefb391c5757934d5fd6d461e5a1231e1a080ca291187706ad5d46444e9
Timestamp: 1730979713 Timestamp [UCT]: 2024-11-07 11:41:53 Age [y:d:h:m:s]: 00:161:17:26:29
Block: 1148497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115422 RingCT/type: yes/0
Extra: 01cb946aefb391c5757934d5fd6d461e5a1231e1a080ca291187706ad5d46444e90211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01aaff7b21b796fd8445b094515cb82d38b472d55a7919e2a355f9ae264aad47 0.600000000000 1633360 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": 1148507, "vin": [ { "gen": { "height": 1148497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01aaff7b21b796fd8445b094515cb82d38b472d55a7919e2a355f9ae264aad47" } } ], "extra": [ 1, 203, 148, 106, 239, 179, 145, 197, 117, 121, 52, 213, 253, 109, 70, 30, 90, 18, 49, 225, 160, 128, 202, 41, 17, 135, 112, 106, 213, 212, 100, 68, 233, 2, 17, 0, 0, 0, 9, 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