Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c70f11fb2ef3b8125b9cd395ddb4f2f527aea40331e98dc84cbee6a8e6afdb3

Tx prefix hash: bd552ae311e070fe7b5adcbce6f9d3758fb11b2af5b79443ddf26ba8138a0c25
Tx public key: e56033c8d4d38f09e2ec18d0815c49d5ae82ea7b14bd9e9f6036ae2d462a2ebb
Timestamp: 1721125109 Timestamp [UCT]: 2024-07-16 10:18:29 Age [y:d:h:m:s]: 00:282:00:36:18
Block: 1066897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201488 RingCT/type: yes/0
Extra: 01e56033c8d4d38f09e2ec18d0815c49d5ae82ea7b14bd9e9f6036ae2d462a2ebb021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a98b2124f825ee8d56dcf7840163c369e9401c2f2243e843d5ff902dbd03ae0 0.600000000000 1537574 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": 1066907, "vin": [ { "gen": { "height": 1066897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a98b2124f825ee8d56dcf7840163c369e9401c2f2243e843d5ff902dbd03ae0" } } ], "extra": [ 1, 229, 96, 51, 200, 212, 211, 143, 9, 226, 236, 24, 208, 129, 92, 73, 213, 174, 130, 234, 123, 20, 189, 158, 159, 96, 54, 174, 45, 70, 42, 46, 187, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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