Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64417a1a7e6b5ff86201e29455a5d62d388da7265a21729df61a80dcdaf8976b

Tx prefix hash: c41e8040e0b7c5959a142186852c9c805e35408e47898f5fcf8da78e361e867f
Tx public key: dd423bd1a694a2d26c695cf90cfbac4a33fb83ca1ced1922ea40f255a6c7e47e
Timestamp: 1706851895 Timestamp [UCT]: 2024-02-02 05:31:35 Age [y:d:h:m:s]: 01:112:07:53:50
Block: 948544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341380 RingCT/type: yes/0
Extra: 01dd423bd1a694a2d26c695cf90cfbac4a33fb83ca1ced1922ea40f255a6c7e47e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cee3a825fcea2a78977bc677617b661823df1a4889aec7071c1fec5edf4e80a5 0.600000000000 1406972 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": 948554, "vin": [ { "gen": { "height": 948544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cee3a825fcea2a78977bc677617b661823df1a4889aec7071c1fec5edf4e80a5" } } ], "extra": [ 1, 221, 66, 59, 209, 166, 148, 162, 210, 108, 105, 92, 249, 12, 251, 172, 74, 51, 251, 131, 202, 28, 237, 25, 34, 234, 64, 242, 85, 166, 199, 228, 126, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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