Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c42f5380e7955cf33b2b77035d166847c83ac34a6bbca489eaf4e3b65f8f95f0

Tx prefix hash: 29c5373a1d8f75bc394a09fda41450b5fc31b646b210212429106c56b6a209ce
Tx public key: d40ea1fe7c3e2b741399e81841063b9c99d3ce786bb22bed75213918d1b045c4
Timestamp: 1716080638 Timestamp [UCT]: 2024-05-19 01:03:58 Age [y:d:h:m:s]: 00:236:20:07:14
Block: 1025063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169509 RingCT/type: yes/0
Extra: 01d40ea1fe7c3e2b741399e81841063b9c99d3ce786bb22bed75213918d1b045c40211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b14c328c075a5c99a9590e62122748c946d8cd540491b7a68a85078a189388e5 0.600000000000 1491290 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": 1025073, "vin": [ { "gen": { "height": 1025063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b14c328c075a5c99a9590e62122748c946d8cd540491b7a68a85078a189388e5" } } ], "extra": [ 1, 212, 14, 161, 254, 124, 62, 43, 116, 19, 153, 232, 24, 65, 6, 59, 156, 153, 211, 206, 120, 107, 178, 43, 237, 117, 33, 57, 24, 209, 176, 69, 196, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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