Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779f6999e6f2de68ffb383397d99b3155bb966469b8dbb7e19a1b87b1e497bb3

Tx prefix hash: 4a1d108a570b37971934857cf4ccf026c4b24963a20388a26ea936f1f21a327f
Tx public key: b6b85e2c5b2cc4579ec3842942bd585e9739d5a1c5afd15791dc65840ba93f71
Timestamp: 1717738029 Timestamp [UCT]: 2024-06-07 05:27:09 Age [y:d:h:m:s]: 00:178:12:17:27
Block: 1038809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127761 RingCT/type: yes/0
Extra: 01b6b85e2c5b2cc4579ec3842942bd585e9739d5a1c5afd15791dc65840ba93f710211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb47a853352face4b6e0c092ffbbbe60a216ceca38b612577d9ea970fd070dc1 0.600000000000 1507370 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": 1038819, "vin": [ { "gen": { "height": 1038809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb47a853352face4b6e0c092ffbbbe60a216ceca38b612577d9ea970fd070dc1" } } ], "extra": [ 1, 182, 184, 94, 44, 91, 44, 196, 87, 158, 195, 132, 41, 66, 189, 88, 94, 151, 57, 213, 161, 197, 175, 209, 87, 145, 220, 101, 132, 11, 169, 63, 113, 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