Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41d6ac8727fb599e9043655ebf4e644f8596115a9b1e7c36d655211af410fef0

Tx prefix hash: 4876c45314a21b75e081bdf2c3f72ef5ca6f1fc37a1808c0112e8be7c93d0dde
Tx public key: d44783a6844ab87aea82a32b2fe4fa409c6034cbd1417648e5b225c3c513e6b6
Timestamp: 1682535455 Timestamp [UCT]: 2023-04-26 18:57:35 Age [y:d:h:m:s]: 01:204:15:58:59
Block: 747206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407717 RingCT/type: yes/0
Extra: 01d44783a6844ab87aea82a32b2fe4fa409c6034cbd1417648e5b225c3c513e6b60211000000037e406890000000000000000000

1 output(s) for total of 2.052090686000 dcy

stealth address amount amount idx
00: f10094a214cdad28be8d7d2146897b9ded58733659a5ee15c98213bbb6c61101 2.052090686000 1194853 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": 747216, "vin": [ { "gen": { "height": 747206 } } ], "vout": [ { "amount": 2052090686, "target": { "key": "f10094a214cdad28be8d7d2146897b9ded58733659a5ee15c98213bbb6c61101" } } ], "extra": [ 1, 212, 71, 131, 166, 132, 74, 184, 122, 234, 130, 163, 43, 47, 228, 250, 64, 156, 96, 52, 203, 209, 65, 118, 72, 229, 178, 37, 195, 197, 19, 230, 182, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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