Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc1460d2c71c94367007fb3552f97b668724d4da0e7557f9f47d4494a35df638

Tx prefix hash: c95099dac5e7fdeece321b109703b93fac9a8a1559f88c21a5f488522fec68ea
Tx public key: b4f54bc3aff929cf1ac15496f732e475d3341f0f1094f39cef403d94dcb3b169
Timestamp: 1734912887 Timestamp [UCT]: 2024-12-23 00:14:47 Age [y:d:h:m:s]: 00:102:17:41:42
Block: 1181103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73182 RingCT/type: yes/0
Extra: 01b4f54bc3aff929cf1ac15496f732e475d3341f0f1094f39cef403d94dcb3b16902110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a361958f547bbd1f25305ef8f5887cc6ee0180550f96ac5b2fbb123a2f6b22a 0.600000000000 1667518 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": 1181113, "vin": [ { "gen": { "height": 1181103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a361958f547bbd1f25305ef8f5887cc6ee0180550f96ac5b2fbb123a2f6b22a" } } ], "extra": [ 1, 180, 245, 75, 195, 175, 249, 41, 207, 26, 193, 84, 150, 247, 50, 228, 117, 211, 52, 31, 15, 16, 148, 243, 156, 239, 64, 61, 148, 220, 179, 177, 105, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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