Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efef98bd25481e31eacbd511b4bf7bdba8479c83b6edc1179e9fd0d27e884e69

Tx prefix hash: f4725a16cdcfef361dcab999e39a60832181c6dcf0c456a2848497a55010fe7e
Tx public key: 83674b0596c4e1ab85bd642d369909747da6c2618cb36cf11d1ee5a073d57d63
Timestamp: 1713191649 Timestamp [UCT]: 2024-04-15 14:34:09 Age [y:d:h:m:s]: 01:031:12:13:47
Block: 1001101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283500 RingCT/type: yes/0
Extra: 0183674b0596c4e1ab85bd642d369909747da6c2618cb36cf11d1ee5a073d57d6302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6c31a34f4f50e8ea0eb029c7dc1a11a0423911a83a0883d33029d3e9649ff0c 0.600000000000 1461603 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": 1001111, "vin": [ { "gen": { "height": 1001101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6c31a34f4f50e8ea0eb029c7dc1a11a0423911a83a0883d33029d3e9649ff0c" } } ], "extra": [ 1, 131, 103, 75, 5, 150, 196, 225, 171, 133, 189, 100, 45, 54, 153, 9, 116, 125, 166, 194, 97, 140, 179, 108, 241, 29, 30, 229, 160, 115, 213, 125, 99, 2, 17, 0, 0, 0, 2, 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