Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc5924f3772f6b06eab48fadfcaf5ef29fb35abb8a67b00e9991039de37523d0

Tx prefix hash: 56fdf76d111bbe824e07a98c26942c6038842a7ce84badb63c7cba4a3d17a6ab
Tx public key: 8a64c6707974686c1cdab97cf6505b28b5e5afbeb67802f1702e4b396f643dc5
Timestamp: 1730534303 Timestamp [UCT]: 2024-11-02 07:58:23 Age [y:d:h:m:s]: 00:180:13:08:47
Block: 1144795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128899 RingCT/type: yes/0
Extra: 018a64c6707974686c1cdab97cf6505b28b5e5afbeb67802f1702e4b396f643dc50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa254a5b52b8081bb86b37fbe6551e423ece813f307a50ae25494fca5bcaf947 0.600000000000 1629108 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": 1144805, "vin": [ { "gen": { "height": 1144795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa254a5b52b8081bb86b37fbe6551e423ece813f307a50ae25494fca5bcaf947" } } ], "extra": [ 1, 138, 100, 198, 112, 121, 116, 104, 108, 28, 218, 185, 124, 246, 80, 91, 40, 181, 229, 175, 190, 182, 120, 2, 241, 112, 46, 75, 57, 111, 100, 61, 197, 2, 17, 0, 0, 0, 3, 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