Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cbcfa90bcf7ed4842520ba67e341c92bc00c0076c7a14389ff4dfd0e853a4c0

Tx prefix hash: 5a123152b825935ab8aacf6153a9e6e376f3df6acba6c029ff26e6843b1b9104
Tx public key: 468fe2e028db7852a5530665a1412ed206d0b39fbe712ee983b639e830b4489f
Timestamp: 1729299894 Timestamp [UCT]: 2024-10-19 01:04:54 Age [y:d:h:m:s]: 00:238:03:59:36
Block: 1134654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169959 RingCT/type: yes/0
Extra: 01468fe2e028db7852a5530665a1412ed206d0b39fbe712ee983b639e830b4489f0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36970256fd2a0a04414ed60a78aa142850964a1f801fa8d35c4e4b5e8498a52f 0.600000000000 1617979 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": 1134664, "vin": [ { "gen": { "height": 1134654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36970256fd2a0a04414ed60a78aa142850964a1f801fa8d35c4e4b5e8498a52f" } } ], "extra": [ 1, 70, 143, 226, 224, 40, 219, 120, 82, 165, 83, 6, 101, 161, 65, 46, 210, 6, 208, 179, 159, 190, 113, 46, 233, 131, 182, 57, 232, 48, 180, 72, 159, 2, 17, 0, 0, 0, 9, 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