Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28e25daabeb28e0828e70dba0a297529c4c26a5532942124f904e4ec1974b566

Tx prefix hash: 4583d932a157d038268faed7b5c5a684903d6c319f08a0ed5f2b2b8df1aa33c3
Tx public key: ef7cf41115178bb75094c074e35e29ff7cfa96b94662c9a885021368d6620a15
Timestamp: 1708075585 Timestamp [UCT]: 2024-02-16 09:26:25 Age [y:d:h:m:s]: 01:047:16:32:49
Block: 958684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295118 RingCT/type: yes/0
Extra: 01ef7cf41115178bb75094c074e35e29ff7cfa96b94662c9a885021368d6620a150211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 757d34cc80d4a5a41c1d6ea3062f3a44265c2eb8b14c5e029b2a40b1b43c5f95 0.600000000000 1418045 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": 958694, "vin": [ { "gen": { "height": 958684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "757d34cc80d4a5a41c1d6ea3062f3a44265c2eb8b14c5e029b2a40b1b43c5f95" } } ], "extra": [ 1, 239, 124, 244, 17, 21, 23, 139, 183, 80, 148, 192, 116, 227, 94, 41, 255, 124, 250, 150, 185, 70, 98, 201, 168, 133, 2, 19, 104, 214, 98, 10, 21, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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