Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13758441fa555a99955d2c9fa2bcf1759a9186be7cbd194debbe78a3d7eab6e2

Tx prefix hash: c2f6d48cfc8e432ab00dc9a02504966cf71763e44eee91b7e2dc6666521ad056
Tx public key: 352c417c1924ee1ad5f832e31835660fe9be753f8eef78458ab4f4d505866d9f
Timestamp: 1719285323 Timestamp [UCT]: 2024-06-25 03:15:23 Age [y:d:h:m:s]: 00:263:12:43:51
Block: 1051621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188322 RingCT/type: yes/0
Extra: 01352c417c1924ee1ad5f832e31835660fe9be753f8eef78458ab4f4d505866d9f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61e0b8c90a7063315b6873c81e9dbfef63240c9def0cb111bd8fcf28823ff61b 0.600000000000 1521936 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": 1051631, "vin": [ { "gen": { "height": 1051621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61e0b8c90a7063315b6873c81e9dbfef63240c9def0cb111bd8fcf28823ff61b" } } ], "extra": [ 1, 53, 44, 65, 124, 25, 36, 238, 26, 213, 248, 50, 227, 24, 53, 102, 15, 233, 190, 117, 63, 142, 239, 120, 69, 138, 180, 244, 213, 5, 134, 109, 159, 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