Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d991789186bd564633e01ae58f0be7a37b2ee0b9d3f24fbe29b29ee7b7cad01

Tx prefix hash: 12779de69a5efd843be812d651fe61761426d43cae793a60aeadf6799fa4c2fa
Tx public key: 4c87582d711a816af67a5d4076ae91258d486dfcc8c48c76f9750029f25b34dc
Timestamp: 1730116675 Timestamp [UCT]: 2024-10-28 11:57:55 Age [y:d:h:m:s]: 01:039:06:10:02
Block: 1141355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286510 RingCT/type: yes/0
Extra: 014c87582d711a816af67a5d4076ae91258d486dfcc8c48c76f9750029f25b34dc021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 786dded7f116795b6298fbce35f18815bd2f868854912ba72fbeccd82a3b9f0a 0.600000000000 1625162 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": 1141365, "vin": [ { "gen": { "height": 1141355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "786dded7f116795b6298fbce35f18815bd2f868854912ba72fbeccd82a3b9f0a" } } ], "extra": [ 1, 76, 135, 88, 45, 113, 26, 129, 106, 246, 122, 93, 64, 118, 174, 145, 37, 141, 72, 109, 252, 200, 196, 140, 118, 249, 117, 0, 41, 242, 91, 52, 220, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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