Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e6ba45784af54a002d6362668bf95cc21fc553864a92299a1571dc94813b853

Tx prefix hash: 24c2b43eb6e181c5fcbbc3c709a7cfd56f7dd0abf15cba4dea12b6c172a5c515
Tx public key: 969ad6b1184bd4f3b79dd11e7c63db3cd95837fb5d23606e19e08b5aaa4f3f9a
Timestamp: 1722075783 Timestamp [UCT]: 2024-07-27 10:23:03 Age [y:d:h:m:s]: 00:311:19:44:06
Block: 1074769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222812 RingCT/type: yes/0
Extra: 01969ad6b1184bd4f3b79dd11e7c63db3cd95837fb5d23606e19e08b5aaa4f3f9a02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77d372f1ed8049a5847910f5488b5aefdf8cc35a46750003848c9cecd432c2de 0.600000000000 1547288 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": 1074779, "vin": [ { "gen": { "height": 1074769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77d372f1ed8049a5847910f5488b5aefdf8cc35a46750003848c9cecd432c2de" } } ], "extra": [ 1, 150, 154, 214, 177, 24, 75, 212, 243, 183, 157, 209, 30, 124, 99, 219, 60, 217, 88, 55, 251, 93, 35, 96, 110, 25, 224, 139, 90, 170, 79, 63, 154, 2, 17, 0, 0, 0, 13, 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