Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecfbbd450632c5ffb58e2ceccdead20d51278c611d40377a6c68d5d9f0a288d4

Tx prefix hash: e33eacb91a868ae7172bc36bb90cee7759a02345f475b276a0da7e2dcfca5b1a
Tx public key: a712afd1bc4c190337070feb6fda676d93430f37d6b0ef7d3d4d24f19937fd99
Timestamp: 1724593492 Timestamp [UCT]: 2024-08-25 13:44:52 Age [y:d:h:m:s]: 00:263:07:49:45
Block: 1095635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188091 RingCT/type: yes/0
Extra: 01a712afd1bc4c190337070feb6fda676d93430f37d6b0ef7d3d4d24f19937fd9902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a47c2295114658ad6d7a0d86a655d301e995caf4da27a1d0e2ff00e127eca735 0.600000000000 1570816 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": 1095645, "vin": [ { "gen": { "height": 1095635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a47c2295114658ad6d7a0d86a655d301e995caf4da27a1d0e2ff00e127eca735" } } ], "extra": [ 1, 167, 18, 175, 209, 188, 76, 25, 3, 55, 7, 15, 235, 111, 218, 103, 109, 147, 67, 15, 55, 214, 176, 239, 125, 61, 77, 36, 241, 153, 55, 253, 153, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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