Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ee8f0a3f565271f905effedac4f1bdb45a4e54bdf89d835bb701bd5b9088b04

Tx prefix hash: ce28be8030b2059ebd7a4b646d7f0ce1ebf5f0fd946f71ce25707fc61a00c593
Tx public key: 70ed3e116bfe8fb379b8c5db7edde84466e5140840a84c93c091fcd9eb0367ed
Timestamp: 1727781197 Timestamp [UCT]: 2024-10-01 11:13:17 Age [y:d:h:m:s]: 00:176:00:11:16
Block: 1122070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125564 RingCT/type: yes/0
Extra: 0170ed3e116bfe8fb379b8c5db7edde84466e5140840a84c93c091fcd9eb0367ed02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f34944d1350a5f4db6ec01f134ea6309b5aa703a23858144dbce05ae3ef4dc1d 0.600000000000 1604441 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": 1122080, "vin": [ { "gen": { "height": 1122070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f34944d1350a5f4db6ec01f134ea6309b5aa703a23858144dbce05ae3ef4dc1d" } } ], "extra": [ 1, 112, 237, 62, 17, 107, 254, 143, 179, 121, 184, 197, 219, 126, 221, 232, 68, 102, 229, 20, 8, 64, 168, 76, 147, 192, 145, 252, 217, 235, 3, 103, 237, 2, 17, 0, 0, 0, 12, 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