Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 051ad3451e1f7a78b811723ba1ed4b559135e5034721f0de74ef241d68a28599

Tx prefix hash: 1df9caab395d0fd4689c5336ef6bc77e970d4b2fcd071a88dbd97735f354b046
Tx public key: 9df8a86e569f5082c7a3b0319b3dc8313ddd36d73d60b31e69fa992860d6ac36
Timestamp: 1731014259 Timestamp [UCT]: 2024-11-07 21:17:39 Age [y:d:h:m:s]: 00:016:09:30:30
Block: 1148784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11730 RingCT/type: yes/0
Extra: 019df8a86e569f5082c7a3b0319b3dc8313ddd36d73d60b31e69fa992860d6ac360211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51bea24b36eafd37e047beda43456a51de267bbb70ca8501cd130de903e66f02 0.600000000000 1633709 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": 1148794, "vin": [ { "gen": { "height": 1148784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51bea24b36eafd37e047beda43456a51de267bbb70ca8501cd130de903e66f02" } } ], "extra": [ 1, 157, 248, 168, 110, 86, 159, 80, 130, 199, 163, 176, 49, 155, 61, 200, 49, 61, 221, 54, 215, 61, 96, 179, 30, 105, 250, 153, 40, 96, 214, 172, 54, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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