Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 434b83a98295d254b39ddab8469e754c6ae0f0a4db5614b04ba2d907697d4ce3

Tx prefix hash: 328424d6c7b2865637c31fea569334355c06ba9df049be76750042a7e801a472
Tx public key: 4d825b19d7968387b0e15f7bb2660c78f09ab0914f9e15c4a23ec5de011397a8
Timestamp: 1730400244 Timestamp [UCT]: 2024-10-31 18:44:04 Age [y:d:h:m:s]: 00:341:22:08:01
Block: 1143700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241875 RingCT/type: yes/0
Extra: 014d825b19d7968387b0e15f7bb2660c78f09ab0914f9e15c4a23ec5de011397a8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 988635524e524ce2683c871b30b1a1011d2b1a7f8c7adcd85b23841ec094ba36 0.600000000000 1627661 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": 1143710, "vin": [ { "gen": { "height": 1143700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "988635524e524ce2683c871b30b1a1011d2b1a7f8c7adcd85b23841ec094ba36" } } ], "extra": [ 1, 77, 130, 91, 25, 215, 150, 131, 135, 176, 225, 95, 123, 178, 102, 12, 120, 240, 154, 176, 145, 79, 158, 21, 196, 162, 62, 197, 222, 1, 19, 151, 168, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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