Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 181e9490e160d86f93746f73fec166eb0c63bd0a9db1de794d474c1fd22139ba

Tx prefix hash: 2e81e5793c3bcf67174d81363c46b5cbdbc1025dc10249f2174d0d7da065e585
Tx public key: 8259e0daa2d313ae8318c2c30adfbf8207bc7ec1a134c2b29d423d5931adcbdf
Timestamp: 1710662258 Timestamp [UCT]: 2024-03-17 07:57:38 Age [y:d:h:m:s]: 01:261:12:49:01
Block: 980163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445639 RingCT/type: yes/0
Extra: 018259e0daa2d313ae8318c2c30adfbf8207bc7ec1a134c2b29d423d5931adcbdf0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 463361b09e427129e70ab2fa4a9dcd9709583caf63bd78c37b7ddccce352950a 0.600000000000 1440222 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": 980173, "vin": [ { "gen": { "height": 980163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "463361b09e427129e70ab2fa4a9dcd9709583caf63bd78c37b7ddccce352950a" } } ], "extra": [ 1, 130, 89, 224, 218, 162, 211, 19, 174, 131, 24, 194, 195, 10, 223, 191, 130, 7, 188, 126, 193, 161, 52, 194, 178, 157, 66, 61, 89, 49, 173, 203, 223, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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