Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f1bc57b20bf79ab6e20534294a94eadd130cfb2bed44f98845c32cd66a07da9

Tx prefix hash: e3c0d216fb396df55fb7c09852d008469cf5baae47a0dbffc57a8b72f350411e
Tx public key: 2dc21f19f451765981c64ff52fe38142df531d38c564d2f44526e40458826d3f
Timestamp: 1710239408 Timestamp [UCT]: 2024-03-12 10:30:08 Age [y:d:h:m:s]: 01:078:05:13:48
Block: 976653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316922 RingCT/type: yes/0
Extra: 012dc21f19f451765981c64ff52fe38142df531d38c564d2f44526e40458826d3f02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c003d3fb89f9e71ae1c7f16783253ea4b22ea46aa88c27cd305c36726da7b36e 0.600000000000 1436648 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": 976663, "vin": [ { "gen": { "height": 976653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c003d3fb89f9e71ae1c7f16783253ea4b22ea46aa88c27cd305c36726da7b36e" } } ], "extra": [ 1, 45, 194, 31, 25, 244, 81, 118, 89, 129, 198, 79, 245, 47, 227, 129, 66, 223, 83, 29, 56, 197, 100, 210, 244, 69, 38, 228, 4, 88, 130, 109, 63, 2, 17, 0, 0, 0, 8, 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