Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e41e49e6c0c0a18b10e69577b84df94d6e0211da1fa872c3ee42808bd925783

Tx prefix hash: 8b1498b7649648053c8f407a5fd9e941e0c4c84b3bfcb2a4309fee0568352631
Tx public key: 0015f696ee476829c7eaf1aa8720eacf931aaa11666491f18512e023b323b5ae
Timestamp: 1717824612 Timestamp [UCT]: 2024-06-08 05:30:12 Age [y:d:h:m:s]: 00:215:06:16:34
Block: 1039522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154053 RingCT/type: yes/0
Extra: 010015f696ee476829c7eaf1aa8720eacf931aaa11666491f18512e023b323b5ae02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dbda34f853322ea614948964aa639f42518c3ddc4f58fd17d8d6263f24c33cd 0.600000000000 1508165 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": 1039532, "vin": [ { "gen": { "height": 1039522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dbda34f853322ea614948964aa639f42518c3ddc4f58fd17d8d6263f24c33cd" } } ], "extra": [ 1, 0, 21, 246, 150, 238, 71, 104, 41, 199, 234, 241, 170, 135, 32, 234, 207, 147, 26, 170, 17, 102, 100, 145, 241, 133, 18, 224, 35, 179, 35, 181, 174, 2, 17, 0, 0, 0, 1, 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