Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bf2f9d8f0f3b3167bbe23fb767af1b218e63f8504dc7c7d79cba27d769e7059

Tx prefix hash: 49f854ef4f7ade47cc0f5c890f1ddd8792778708fb582fefe2e4ae8d51210f5f
Tx public key: 261f0e8e04b7f969cfbe91f205b3aea09fde2da2c9871d5be987ea3f7e2ed14b
Timestamp: 1736828568 Timestamp [UCT]: 2025-01-14 04:22:48 Age [y:d:h:m:s]: 00:155:18:43:24
Block: 1196937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111026 RingCT/type: yes/0
Extra: 01261f0e8e04b7f969cfbe91f205b3aea09fde2da2c9871d5be987ea3f7e2ed14b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 722ab74d266cd5720d5adb39372cdcf9d7a0a53903fb6877b5b9ac63720f54e1 0.600000000000 1683542 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": 1196947, "vin": [ { "gen": { "height": 1196937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722ab74d266cd5720d5adb39372cdcf9d7a0a53903fb6877b5b9ac63720f54e1" } } ], "extra": [ 1, 38, 31, 14, 142, 4, 183, 249, 105, 207, 190, 145, 242, 5, 179, 174, 160, 159, 222, 45, 162, 201, 135, 29, 91, 233, 135, 234, 63, 126, 46, 209, 75, 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