Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e135c10e647aebefc2938207eee86c6f314f0bc01695278b0f2e6a869f896f

Tx prefix hash: dd789e3466f64441d426fa50254510dfa12601dd3b6f0d17fa0489c2775b7783
Tx public key: bd49d73eefc474ae3331edab390937ba20c9c78bae6934c0c6fb322311a42c7d
Timestamp: 1722260039 Timestamp [UCT]: 2024-07-29 13:33:59 Age [y:d:h:m:s]: 00:250:04:28:38
Block: 1076294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178712 RingCT/type: yes/0
Extra: 01bd49d73eefc474ae3331edab390937ba20c9c78bae6934c0c6fb322311a42c7d021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2675627ed3f6b0b6752b9f99e95e2a4e32f18c2d871d95906e83be55a71ef8bc 0.600000000000 1548831 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": 1076304, "vin": [ { "gen": { "height": 1076294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2675627ed3f6b0b6752b9f99e95e2a4e32f18c2d871d95906e83be55a71ef8bc" } } ], "extra": [ 1, 189, 73, 215, 62, 239, 196, 116, 174, 51, 49, 237, 171, 57, 9, 55, 186, 32, 201, 199, 139, 174, 105, 52, 192, 198, 251, 50, 35, 17, 164, 44, 125, 2, 17, 0, 0, 0, 8, 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