Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a6969f7bde1e2b0bb7a8f4c76f57935d9a16910dc52b80d0605f9e8b5157a25

Tx prefix hash: 01cdcc89b0ce4689cf2ef02786730722b6e32b1e863193ae43a29ec26dd9b43a
Tx public key: 8ab0344dd8e131b8f1fefe1fa7759928de698670c32d2a92a6ef7072a5e823ce
Timestamp: 1719923552 Timestamp [UCT]: 2024-07-02 12:32:32 Age [y:d:h:m:s]: 00:294:16:55:21
Block: 1056924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210571 RingCT/type: yes/0
Extra: 018ab0344dd8e131b8f1fefe1fa7759928de698670c32d2a92a6ef7072a5e823ce02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c46a97ea1525f6cdc6d81684325c890c7d0a1db7e13207d79907b5f1826c975 0.600000000000 1527353 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": 1056934, "vin": [ { "gen": { "height": 1056924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c46a97ea1525f6cdc6d81684325c890c7d0a1db7e13207d79907b5f1826c975" } } ], "extra": [ 1, 138, 176, 52, 77, 216, 225, 49, 184, 241, 254, 254, 31, 167, 117, 153, 40, 222, 105, 134, 112, 195, 45, 42, 146, 166, 239, 112, 114, 165, 232, 35, 206, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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