Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99018423a938de161c43665d10b4bc1a2a4b0f7ad67840481073d97b101ad8b6

Tx prefix hash: b530a995a9963e3d893ad558042b4e90d224ab601978a0b5f92a40fd04a1a878
Tx public key: 659a518bf8499dbd75b5e5c95be6e78681345893dc2a75ee3b32a1a503da62da
Timestamp: 1726036576 Timestamp [UCT]: 2024-09-11 06:36:16 Age [y:d:h:m:s]: 00:210:20:54:47
Block: 1107604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150546 RingCT/type: yes/0
Extra: 01659a518bf8499dbd75b5e5c95be6e78681345893dc2a75ee3b32a1a503da62da02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aa56d13d96097fdb21ce4917a4db3bb8b46116452739a7997db631326dcae48 0.600000000000 1585217 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": 1107614, "vin": [ { "gen": { "height": 1107604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aa56d13d96097fdb21ce4917a4db3bb8b46116452739a7997db631326dcae48" } } ], "extra": [ 1, 101, 154, 81, 139, 248, 73, 157, 189, 117, 181, 229, 201, 91, 230, 231, 134, 129, 52, 88, 147, 220, 42, 117, 238, 59, 50, 161, 165, 3, 218, 98, 218, 2, 17, 0, 0, 0, 1, 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