Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e9aa06a7afa6f4fbbc6b0c8f8bcab7bbda599d58f1e695851224f9d7db5daa4

Tx prefix hash: 590392b3ea193a9f6ea296f3d61efc58fb07a857c2c008f9c5f79f8830f299b1
Tx public key: 279c9bd2abef45910042b0d2580518917673ebe6e3198affc83a776b44a1ea43
Timestamp: 1726906516 Timestamp [UCT]: 2024-09-21 08:15:16 Age [y:d:h:m:s]: 00:191:13:26:35
Block: 1114814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136723 RingCT/type: yes/0
Extra: 01279c9bd2abef45910042b0d2580518917673ebe6e3198affc83a776b44a1ea4302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b447d1f25be52370db51fa10ee8cc685910e9a1366b4646789e978c2d1ec755 0.600000000000 1594723 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": 1114824, "vin": [ { "gen": { "height": 1114814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b447d1f25be52370db51fa10ee8cc685910e9a1366b4646789e978c2d1ec755" } } ], "extra": [ 1, 39, 156, 155, 210, 171, 239, 69, 145, 0, 66, 176, 210, 88, 5, 24, 145, 118, 115, 235, 230, 227, 25, 138, 255, 200, 58, 119, 107, 68, 161, 234, 67, 2, 17, 0, 0, 0, 2, 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