Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d34f86c38bdaee2794e74daebf06af631fd93d6df491e0ac0407c31f314ad6

Tx prefix hash: 58f347f99cd7fb868b938eba8d79f3b147ccff079d477800f5e9ff039c817cac
Tx public key: a785108283a5c48ac2ea6d1430a9d10ae8cbe9dfb072a57046592533404289e0
Timestamp: 1715001187 Timestamp [UCT]: 2024-05-06 13:13:07 Age [y:d:h:m:s]: 00:240:01:39:12
Block: 1016109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171831 RingCT/type: yes/0
Extra: 01a785108283a5c48ac2ea6d1430a9d10ae8cbe9dfb072a57046592533404289e002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ab521d7c8410ce0915866b3703914bb781fbfcac1fda936b39d37375bf6e618 0.600000000000 1479600 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": 1016119, "vin": [ { "gen": { "height": 1016109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ab521d7c8410ce0915866b3703914bb781fbfcac1fda936b39d37375bf6e618" } } ], "extra": [ 1, 167, 133, 16, 130, 131, 165, 196, 138, 194, 234, 109, 20, 48, 169, 209, 10, 232, 203, 233, 223, 176, 114, 165, 112, 70, 89, 37, 51, 64, 66, 137, 224, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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