Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff06c43b5b121b6e362b164a45ecddceb789336c89325529a24f7622bd3c593

Tx prefix hash: 4f1e4167552496c20848c4e963a77e842b66ab058937e04f77f60a9ffcc5c5a0
Tx public key: 437b852db5766877db5619c88a2de86a4fda3833fd334e654996722e0be54f3e
Timestamp: 1701587769 Timestamp [UCT]: 2023-12-03 07:16:09 Age [y:d:h:m:s]: 01:083:02:20:05
Block: 904897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320516 RingCT/type: yes/0
Extra: 01437b852db5766877db5619c88a2de86a4fda3833fd334e654996722e0be54f3e021100000004faf35c9c000000000000000000

1 output(s) for total of 0.616170035000 dcy

stealth address amount amount idx
00: 0bd87d35c3c60647ef4f41df2cf393998cdf62e3374a0dc17fa6bc98b0c46a41 0.616170035000 1361682 of 0

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": 904907, "vin": [ { "gen": { "height": 904897 } } ], "vout": [ { "amount": 616170035, "target": { "key": "0bd87d35c3c60647ef4f41df2cf393998cdf62e3374a0dc17fa6bc98b0c46a41" } } ], "extra": [ 1, 67, 123, 133, 45, 181, 118, 104, 119, 219, 86, 25, 200, 138, 45, 232, 106, 79, 218, 56, 51, 253, 51, 78, 101, 73, 150, 114, 46, 11, 229, 79, 62, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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