Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4765b91a2ec223c614a1a00855a44795473d5874598269ef554155b3f053048e

Tx prefix hash: 6707d6a51c5d6fbea91088bc228c4204d175354e942fd7bfe380e66d6732cc5a
Tx public key: 5160a74948d67f4a893e12acc4d4a6954808c25a2b3320dac40dfad324d93ca4
Timestamp: 1728391203 Timestamp [UCT]: 2024-10-08 12:40:03 Age [y:d:h:m:s]: 00:220:22:13:44
Block: 1127122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157716 RingCT/type: yes/0
Extra: 015160a74948d67f4a893e12acc4d4a6954808c25a2b3320dac40dfad324d93ca4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ac43a85557c9adc46cf168332d73c30fcd41716df256cb7e817bad1ea580ce3 0.600000000000 1609921 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": 1127132, "vin": [ { "gen": { "height": 1127122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ac43a85557c9adc46cf168332d73c30fcd41716df256cb7e817bad1ea580ce3" } } ], "extra": [ 1, 81, 96, 167, 73, 72, 214, 127, 74, 137, 62, 18, 172, 196, 212, 166, 149, 72, 8, 194, 90, 43, 51, 32, 218, 196, 13, 250, 211, 36, 217, 60, 164, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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