Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9a1fca97a96cb9451fbba62048d8f252b96a7fe0c808cc96e45926428321daf

Tx prefix hash: 46956e55e819480bd0b4d1181d4f64600fb5988fae2b271946d322bc855ffc43
Tx public key: ac15394bb5fa9908db490d696238aa5af223dfd94d99dde9f31612cb087c42b6
Timestamp: 1721843008 Timestamp [UCT]: 2024-07-24 17:43:28 Age [y:d:h:m:s]: 00:300:23:32:02
Block: 1072826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215076 RingCT/type: yes/0
Extra: 01ac15394bb5fa9908db490d696238aa5af223dfd94d99dde9f31612cb087c42b602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ddd7a0245dfac7d986d5b0a119ae0af1f30c28ba31dfd286e43d54aa8aa25df 0.600000000000 1545323 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": 1072836, "vin": [ { "gen": { "height": 1072826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ddd7a0245dfac7d986d5b0a119ae0af1f30c28ba31dfd286e43d54aa8aa25df" } } ], "extra": [ 1, 172, 21, 57, 75, 181, 250, 153, 8, 219, 73, 13, 105, 98, 56, 170, 90, 242, 35, 223, 217, 77, 153, 221, 233, 243, 22, 18, 203, 8, 124, 66, 182, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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