Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1da544a66b3581d75823d1b287686283974dfbad6d463a20ec7a0f8a2f4da04

Tx prefix hash: ddee05e87df90c60ce4123b984d76a00f399e6358c58355e172a2a708657f1a0
Tx public key: 6478b4945ef04758eb20a1224c50397458a89773a00dd9a36f9a2f06b817e125
Timestamp: 1708304986 Timestamp [UCT]: 2024-02-19 01:09:46 Age [y:d:h:m:s]: 00:268:12:28:30
Block: 960594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192262 RingCT/type: yes/0
Extra: 016478b4945ef04758eb20a1224c50397458a89773a00dd9a36f9a2f06b817e12502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9e9edc73b041df7fcd565bd16bb5bdde1829543a7b42d61dacc8be00df90251 0.600000000000 1420179 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": 960604, "vin": [ { "gen": { "height": 960594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9e9edc73b041df7fcd565bd16bb5bdde1829543a7b42d61dacc8be00df90251" } } ], "extra": [ 1, 100, 120, 180, 148, 94, 240, 71, 88, 235, 32, 161, 34, 76, 80, 57, 116, 88, 168, 151, 115, 160, 13, 217, 163, 111, 154, 47, 6, 184, 23, 225, 37, 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