Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6da9ca840a9c54a23f8f4fff114594383bc30dc57e60596a7588e4969aed0d2c

Tx prefix hash: 07fef0e71b403e87850055eddd07c1be14375184f58270fb1f9702d2cca4755b
Tx public key: dd37431216191751d40318b911d5f2d100260c22c7b719197d53ddd4279621e5
Timestamp: 1704884759 Timestamp [UCT]: 2024-01-10 11:05:59 Age [y:d:h:m:s]: 01:123:16:03:48
Block: 932236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349507 RingCT/type: yes/0
Extra: 01dd37431216191751d40318b911d5f2d100260c22c7b719197d53ddd4279621e502110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d652da9ae9d7190d10f608944b20790f5c4b6ae5d0b30f8e3fc88a6599774839 0.600000000000 1390164 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": 932246, "vin": [ { "gen": { "height": 932236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d652da9ae9d7190d10f608944b20790f5c4b6ae5d0b30f8e3fc88a6599774839" } } ], "extra": [ 1, 221, 55, 67, 18, 22, 25, 23, 81, 212, 3, 24, 185, 17, 213, 242, 209, 0, 38, 12, 34, 199, 183, 25, 25, 125, 83, 221, 212, 39, 150, 33, 229, 2, 17, 0, 0, 0, 16, 82, 212, 126, 148, 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